Skip to content

Conversation

@shantanu-gontia
Copy link

@shantanu-gontia shantanu-gontia commented Dec 6, 2025

WORKSPACE are deprecated and to be replaced by MODULE. Bazel roadmap mentions WORKSPACE are going to be removed entirely. Mainline LLVM has also upgraded from WORKSPACE to MODULE.

This PR updates the Torch-MLIR overlay to use MODULE and fixes the bazel build.

  1. WORKSPACE -> MODULE
  2. Add a .bazelversion to 8.4.0 (parity with mainline LLVM)
  3. Update the docker imagefile for the bazel build
  4. Add the AArch64 target to the LLVM Build (to support local builds on Arm)
  5. Update test tooling to support the new MODULE system's idiosynracies

@shantanu-gontia shantanu-gontia marked this pull request as draft December 6, 2025 07:23
@shantanu-gontia shantanu-gontia marked this pull request as ready for review December 7, 2025 09:32
@shantanu-gontia
Copy link
Author

Hi, @sjain-stanford the wiki listed you as the maintainer for the bazel build. Could you review this PR? Thanks.

llvm_config.with_system_environment(["HOME", "INCLUDE", "LIB", "TMP", "TEMP"])

# llvm_config.use_default_substitutions()
llvm_config.use_default_substitutions()
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for FileCheck substitution using @LLVM_TOOLS_DIR@

@sjain-stanford
Copy link
Member

sjain-stanford commented Dec 7, 2025

Hi, @sjain-stanford the wiki listed you as the maintainer for the bazel build. Could you review this PR? Thanks.

Thanks for the ping. I am no longer overseeing the bazel build for torch-mlir but let me loop in someone who can help.
cc: @mfeliz-cruise , @matthewfl (also, we should update the current set of maintainers if possible)

@matthewfl
Copy link
Contributor

I don't have time to take over the maintenance of bazel build files for this.
I see that @asaadaldien is also listed as a maintainer of the bazel build files
https://github.com/llvm/torch-mlir/blob/main/docs/code_owners.md?plain=1#L52C15-L52C28

@sjain-stanford
Copy link
Member

@matthewfl does Cruise need the bazel build going forward? If so, can you re-assign to who needs to review it to make sure the changes are compatible with Cruise's downstream? This was mainly added (and is expected to be supported) by Cruise but neither Ahmed nor I are with Cruise anymore so we need the right maintainers for it going forward.

@matthewfl
Copy link
Contributor

@sjain-stanford bazel is still needed going forward. If there is an issue with bazel then we will have to maintain an internal patch. I don't think that we should be holding up @shantanu-gontia's PR. We will eventually be upgrading bazel and switching to modules, but I don't have a timeline for that.

@shantanu-gontia
Copy link
Author

Thanks @sjain-stanford, @matthewfl

@matthewfl Would you be able to review this PR? Or do you know who would be able to? Since this is my first PR in this project, I don't have access. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants